Task ID-011563 -Support- Issue: A recurring issue with the grid functionality needs attention. The error message, "Itemcode Row3 can't be left empty," appears on the line immediately following the last row in the grid. For example, if one row is present, the error displays on the second line; with two rows, it appears on the third line, and so on. This problem affects multiple screens, not just one. Screenshots are attached for reference.
--> Fixed
Task ID-011442 -- Issue: Reaching out regarding an issue encountered with our reports and screens. Initially, generating any pending report on the screen works correctly. However, after changing the application parameter selection, the report no longer functions as expected. This issue affects all reports and screens across the application when the application parameter is changed.
--> Fixed
Task ID-011565 -- Issue: A problem has been identified where decimal values are displayed in scientific notation (exponential format), preventing records from loading correctly. Trace analysis suggests that an outdated keyword may be the cause. This issue is not restricted to a single screen but affects various scenarios involving decimal values. Screenshots illustrating the problem are attached.
--> Fixed
Task ID-011324 -- Issue:  For non-approvers, it is possible to save and make changes on the screen. However, approvers are unable to save and make changes on the screen; it is throwing an error.
--> Fixed
 
Task ID-011505 -- Issue: MDMap is not working for a particular screen. When records are changed in the target screen, they are not reflected in the source table. However, when we delete the screen and recreate it, the MDMap works correctly. In trace as well the mdmap data are not fetched. PFA
--> @Abinash – As per the analysis based the structure from Dilmah instance,  MDMap  “mastertable” is value is empty , which is causing this issue. This  needs to be investigated at “GoOnline” and MdMap definition structure level. 
 
Task ID-011561 -- Issue:  They have implemented FireSQL delete and insert scripts to manage the 'All Selected Rows' scenario. However, when this scenario is executed, only the last row is being processed. This issue is affecting not only this screen but also everywhere this scenario is used.
--> Finding of this issue as follows:
Script is defined for 'All Selected Rows' as below.
@start
Firesql({d1},{delete samplesalestemp where ( company = :cmp and uname = :username and ivwtype = :iview ) or company is null})
@row
Firesql({i1},{insert into samplesalestemp ( matreqno ,ivwtype, uname , company ) values ( :req_no , :iview, :username , :cmp)})
@end
LoadForm({smiss},{req_no = :req_no~req_date= :req_date~iview= :iview},{p},{True})
 
where : @start & @end scripts parameters suppose to be used from GlobalVars or Iview Param values.  If there is any parameter used from iview column values, then the script needs to be defined @row block.
 
Cause of this issue : @start script, iview column (ivwtype = :iview) used as sql parameter.
 
So, actual script definition needs to be as follows :
 
@start
@row
Firesql({d1},{delete samplesalestemp where ( company = :cmp and uname = :username and ivwtype = :iview ) or company is null})
Firesql({i1},{insert into samplesalestemp ( matreqno ,ivwtype, uname , company ) values ( :req_no , :iview, :username , :cmp)})
@end
LoadForm({smiss},{req_no = :req_no~req_date= :req_date~iview= :iview},{p},{True})
 
                                       
Task ID-011441 -- Issue: The problem with the sum expression not displaying in the fillgrid query is related to the use of the pipe symbol or comma separator which does not appear on the General Purchase Bill screen. This problem may be caused by the pipe symbol or comma separator used in the expression within the link field.
This issue affects all screens in the application where the sum expression is used, not restricted to a specific one. Please find the attached document consisting screenshots for reference.
--> h2a team needs to verify the definition and come back
Task ID-011560 -- Issue:  Show Message script for confirmation purposes, but the result is displaying as Simple instead of Confirmation.
As you discussed with the Dilmah team, this issue has been assigned to you
--> Interactive message not available in axpert web through scripts, requirement needs to be customized